Bitscope programming(http://www.bitscope.com)
                                                                It took me a long time to be able to communicate with Bitscope via a serial port using VEE but I was sure that this versatile language would manage the task. Bitscope echoes back each command and these are received in the "buffer" that is set up by the program(to be read if required). Since we can assume the connection is all right these echoes are superfluous and if left in he buffer only serve to confuse the issue when it comes to receiving data. A typical loading sequence to pre-set the bitscope registers would be----

for          [ 4]@[a]s              to store a hex in register 4
 
 

BITSCOPE @1 (vee IObox)

WRITE TEXT "[" EXEC RESET WRITE TEXT 4 HEX EXEC RESET WRITE TEXT"]" EXEC RESET WRITE TEXT "@"  EXEC RESET WRITE TEXT"[" EXEC RESET WRITE TEXT a HEX EXEC RESET WRITE TEXT"]" EXEC RESET WRITE TEXT "s" EXEC RESET

This is long winded but the variables can be inserted and this command sequence duplicated with different variables. So that the controls can be set up. Notice how EXEC RESET empties the receive buffer. You need this when you have finished setting-up and come to trigger the bitscope to give out its download data. Otherwise the "echoes" will be confused with the download data. When you come to want to read the data just include READ BINARY t BYTE ARRAY 2000. For 2000 bytes of data to be output "t" as set up in bitscope programming guide. I have a development version where I am able to set VEE controls to get various traces. I am now exploring to find which is the best general purpose mode, there seem to have been many changes to "the box" since the original 117 version. In essence the program I have now first loads the registers from the controls, send in a string to set triggering and download mode Once downloaded the data can be manipulated in VEE any way you want.  Happy programming  !!!!

Repeat the basic command box to set all the controls prior to downloading.

Bitscope extra

HOME